Skip to main content

This is a new service – your feedback will help us to improve it.

Tandridge District Council

Tree

There is a problem

  • 1000 entries with tree-protection-order field must match the reference field in the tree protection order

31, 32, 34, 35, 36, 37, 40, 41, 43, 44, 45, 46, 48, 49, 52 WHEELER AVENUE, OXTED

reference
6/2007/TAN T18
name
31, 32, 34, 35, 36, 37, 40, 41, 43, 44, 45, 46, 48, 49, 52 WHEELER AVENUE, OXTED
tree-preservation-order

undefined

6/2007/TAN
uprn
address-text
31, 32, 34, 35, 36, 37, 40, 41, 43, 44, 45, 46, 48, 49, 52 WHEELER AVENUE, OXTED
point
POINT (-0.010890 51.257600)
geometry
MULTIPOLYGON (((-0.010887 51.257639,-0.010919 51.257635,-0.010947 51.257615,-0.010951 51.257598,-0.010938 51.257576,-0.010907 51.257563,-0.010880 51.257562,-0.010836 51.257580,-0.010827 51.257603,-0.010837 51.257622,-0.010887 51.257639)))
notes
organisation
felled-date
entry-date
2007-04-20
start-date
2007-04-20
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

How to improve Tandridge District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL